<?xml version="1.0" encoding="utf-8"?>
<Content xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:blueonionsoftware-com:bloget:runtime:data">
  <text>What changed:

&lt;ul&gt;
	&lt;li&gt;I've added two new configurations: SignedDebug and SignedRelease These configurations build strong named or "signed" versions of the reporting assemblies which are are required for MBox &lt;/li&gt;

	&lt;li&gt;ClinicalReporting is now merged to the Reporting project. This was required to link against the projects to get the correct signed versions. You should modify your nightly build scripts to not build ClinicalReporting solution and just Reporting solution. &lt;/li&gt;

&lt;/ul&gt;

Details:
 
MBox requires all assemblies to be strong named or "signed". Signing has some performance penalties at runtime and can cause build problems since signed assemblies can only reference signed assemblies. I created two new configurations to minimize the "fallout" that might occur had I just signed our existing builds.
 
The two new configurations are SignedDebug and SignedRelease. They build in \build\SignedDebug and \build\SignedRelease respectively. I've tried to minimize the impact of this change as much as possible. With luck, you should not notice any difference other than a minor tweak to your nightly build scripts.
 
Secondly, I moved the three ClinicalReporting projects into the Reporting solution. I need projects references to resolve which assemblies to build against. This will also resolve some other issues with ClinicalReporting that Brian G. wanted addressed. I have a note to myself to remove the ClinicalReporting.sln file in the next couple of days since it will not build correctly for all configurations any longer.
 
All assemblies are signed with a single key pair located in \Report\Build\ReportStrongNameKeyPair.snk. If you add a new project to Reporting, please use this key. Also make sure you only reference the key in the SignedDebug and SignedRelease configurations. You'll have to edit the project files directly to do this since the IDE only supports signing all configurations and not specific configurations.
 
- Mike
</text>
  <last_update>2007-10-04T00:52:33.1270806Z</last_update>
  <source_title />
  <source_link />
  <comments />
  <references />
  <attachments />
</Content>